Columbia Kermit/kermit.zip/newsgroups/misc.19950528-19950726/[e-mail]_Tue Jul 11 14:55:58 1995.msg

Internet Message Format | 2020-01-01 | 2KB

Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA12263
  (5.65c+CU/IDA-1.4.4/HLK for <[e-mail]>); Tue, 11 Jul 1995 10:59:12 -0400
Received: by apakabar.cc.columbia.edu id AA26082
  (5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Tue, 11 Jul 1995 10:59:08 -0400
Path: news.columbia.edu!sol.ctr.columbia.edu!howland.reston.ans.net!gatech!news.mathworks.com!news.duke.edu!godot.cc.duq.edu!hudson.lm.com!newsfeed.pitt.edu!wcbst4
From: [e-mail] (William C Beegle)
Newsgroups: comp.protocols.kermit.misc
Subject: Kermit in ODI
Date: 11 Jul 1995 14:55:58 GMT
Organization: University of Pittsburgh
Lines: 18
Message-Id: <3tu3du$[e-mail]>
Nntp-Posting-Host: unixs2.cis.pitt.edu
Apparently-To: [e-mail]

After spending an absurd amount of time trying to figure out why I
couldn't get MSKermit working with LAN Workplace, I came to a realization:
The Instructions in the /NETWORKS directory need help.  All I had to do
was modify my NET.CFG file.  The setup.doc file talks about using
different frames, but I was already using Ethernet_II.  I ignored the
other differences in the file because I expected differences between the
sample file and my own.  I got everything to work when I added the
    Protocol IP    0800    Ethernet_II
    Protocol ARP    0806    Ethernet_II
    Protocol RARP    8035    Ethernet_II
lines to the NET.CFG file.  The setup file talks about not mixing up IP
and IPX, but I took this as a general warning to pay attention, not a
notice to add the protocol lines from the sample.

--
--
Finger [e-mail] for my PGP public key.
Home - http://www.pitt.edu/~wcbst4